Well Test Overview
CygNet’s Well Test module supports common field configurations for well production facilities, including:
- a Host Mode where the SCADA host sends commands to the field device, for example, read and move valve positions, purge the separator, move wells sequentially from production to test mode one at a time, issue action commands, track values coming from the separator, and abort the test, etc. In this documentation this mode is called a host-based configuration, i.e., the host is managing the sequencing to the PLC or RTU.
- a Device Mode where the well test logic and commands are automated at the device level, and CygNet monitors the well test data coming from the separator facility for each well in test. In this documentation this mode is called a device-based configuration, i.e., the device is managing the sequencing and the host is monitoring the operation.
Configuration and Visualization
The CygNet Well Test model leverages CygNet’s infrastructure to deliver well test results. It supports existing and new device, point and facility configurations; the definition and configuration of well test headers, header templates, and the sequencing of test actions in a dedicated well test configuration control in Canvas; and a powerful XML configuration to replicate device logic. The model performs polling and Set Point actions, uses triggers to initiate and affect the well test process, supports the storage of real-time and historical well test data, and allows visualization of well test data in operational and results screens.
The module includes a CygNet.API.WellTest assembly, which is a .Net API to allow programmatic access to the well test functionality, and a persistent CygNet Well Test Service, which monitors the field device header for valve changes and executes the well test commands. Both components are installed via the CygNet Client Installer.
With unique configurations at the production field level, a programmable approach is necessary to process the well test output. CygNet uses a customizable script to process the output data. Users can apply whatever logic is required to the well test output to produce well test records. The oil rate, water rate, gas rate, well test duration, timestamp of the well test, and a status value (good, bad, or aborted) are combined into a raw well test record and stored as a VHS Blob entry for each configured well. A third-party application can be configured to retrieve CygNet well test records using the CygNet.API.WellTest.
This section describes the well test device logic, the CygNet Well Test module process flow, module components, well test action building blocks, general Canvas configuration, well test configuration in XML, and the sample Canvas operator screens provided with your CygNet installation.
More:
